Building Software Component Architecture Directly from User Requirements

Component Architecture the Software Architecture for Mission Requirements

Software reuse is a common strategy in developing complex systems and has proven successful in reducing labor and maintenance costs. However, simply reusing modules will not produce a system that is adaptable to a variety of mission requirements. Because of this, projects often involve development of similar software systems from scratch in order to satisfy requirements. The end result is a sys...

From requirements negotiation to software architecture decisions

Architecture design and requirements negotiations are conceptually tightly related but often performed separately in real-world software development projects. As our prior case studies have revealed, this separation causes uncertainty in requirements negotiation that hinders progress, limits the success of architecture design, and often leads to wasted effort and substantial re-work later in th...

Component-based Software Engineering: Building Systems from Software Components

Emergency Management: from User Requirements to a Flexible P2P Architecture

The most effective way to design an emergency management system matching user needs is to perform a UserCentered Design; it relies on continuous interactions with end-users in order to understand better and better how organizations are arranged during emergencies, which data are exchanged and which steps are performed by organizations to face disastrous events. In this paper we (i) illustrate t...

Architecture-Driven Software Component Retrieval

This paper argues that retrieval of complex hardware components is based on the use of architectural descriptions rather than functional descriptions, and explores the idea of basing software component retrieval on architectural descriptions. Architecture-driven retrieval is contrasted with retrieval based on keywords that characterize a few relevant properties and with deductive retrieval base...